Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.
Required skills
analytical skills to:
determine functional requirements
identify dynamic client and server-side requirements
communication skills to liaise with the client
initiative and enterprise skills to provide feedback and recommend the most appropriate technology solutions
literacy skills to:
follow documented instruction from a supplied guide
interpret workplace instructions and other technical documents
keep up-to-date with latest industry guidelines
planning and organisational skills to plan and organise the most appropriate solution
problem-solving skills to:
identify and rectify website functional problems
identify and resolve bugs in the code created
select the most efficient and effective algorithms
research skills to:
find solutions to encountered problems
keep up-to-date with industry trends
technical skills to:
apply web programming concepts
create HTML and XHTML pages
create software in a variety of languages, including client and server-side languages
create aesthetically pleasing web pages
understand hypertext transfer protocol (HTTP).
Required knowledge
features of internet technology
principles of analysis and design
programming control structures and object-oriented programming
web programming concepts, including:
authentication and web security
HTTP
session management
stateless programming.
The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.
Document may include: | software requirement specifications unified modelling language (UML) diagrams wireframes. |
Prototype may be in the form of: | images of sample web pages non-functional static website to demonstrate what the site will look like. |
Architectural requirements may be in reference to: | classes required to build the application configuration operating system software. |
Data storage may include: | database files, such as eXtensible markup language (XML). |
Components may include: | classes required to build the application flash movies JavaScript jQuery shopping cart web user controls. |
Design structure may include: | cascading style sheet (CSS) eXtensible hypertext markup language (XHTML). |
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.
Observation Checklist